Comms Monitor
CMP
Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. supports sending communication directly to customers (by letter, email, text, SMS Short Message Service.
A text messaging service component of most mobile telephone systems. SMS uses standardized communication protocols to enable mobile phone devices to exchange short text messages., or push notifications) and indirectly (third party Of software; a reusable component developed to be either freely distributed or sold by an entity other than the original vendor of the development platform. or online account In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices.). Communication to customers is controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically upon receipt of notifications from external systems.
The Comms Monitor job is triggered automatically when new Comms Requests are generated.
This job gathers the details to be included in each individual communication and determines the delivery mechanism, destination and delivery time. Downstream jobs and daemons monitor the output of this job. For example, a document monitor job, such as the Comms Letter Monitor, merges the details with document templates, whereas dedicated daemons distribute communications to the appropriate third parties.
The following daemons are associated with Comms jobs:
| Daemon | Details | ||
|---|---|---|---|
| Load Comms From Generic Format | This daemon collects and decrypts generic CMP files and creates CMP batches, which are available for processing into CMP by the appropriate batch job. | ||
| Transmission Comms Push To Handset | The Push to Handset daemon picks up entries that are ready to be pushed to a handset. These messages contain the full text to be sent and are sent in an encrypted JSON message. | ||
| Acknowledge Comms Receipt Of | The Acknowledgement Daemon takes in a JSON message/file and then updates various values of a particular communication: e.g. an update on the status of a comm from the third party that actually sent it. | ||
| Transmission Comms SMS To Handset | The SMS To Handset Daemon picks up entries that are ready to be sent via SMS. These messages contain the full text to be sent and are sent in an encrypted JSON message. | ||
| Transmission Comms To Document Storage | This daemon places Letters and Emails in long term storage to be accessible via AgentView. | ||
| Transmission Comms To Email | This daemon picks up documents that have to be emailed and sends them to the specified email recipient. | ||
| Extract Comms To Generic Format | This daemon creates and encrypts generic CMP files that are available for conversion to third party format. | ||
| Transmission Comms To Print Bureau | This daemon zips up a directory of letters and sends it to a target location. | ||
The following probe In the Administration Console architecture, a mechanism which allows for the execution of predefined queries and for the comparison of the results of those queries against pre-configured targets. Probes can be reviewed and managed via the Admin Console.(s) can be run against the Comms Monitor job:
| Name | Type | Description | ||
|---|---|---|---|---|
| Comms Monitor Verification Normal | Alert | Alert probe whether errors have been received in the last X number of minutes. | ||
| Comms Monitor Batch Normal | Alert | Alert probe for the count of errors for the current day. | ||
| Comms Monitor Verification Normal | Alert | Alert probe whether there are unprocessed requests in the CommsRequestHeader table. | ||
Relevant JSON schema A specification for JSON based format for defining the structure of JSON data.: